Skip to content

Conversation

ahtesham-quraish
Copy link
Contributor

Description

Describe what this pull request changes, and why. Include implications for people using this change.
Design decisions and their rationales should be documented in the repo (docstring / ADR), per
OEP-19, and can be linked here.

Useful information to include:

  • Which user roles will this change impact? Common user roles are "Learner", "Course Author",
    "Developer", and "Operator".
  • Include screenshots for changes to the UI (ideally, both "before" and "after" screenshots, if applicable).

Supporting information

Link to other information about the change, such as GitHub issues, or Discourse discussions.
Be sure to check they are publicly readable, or if not, repeat the information here.

Testing instructions

Please provide detailed step-by-step instructions for manually testing this change.

Other information

Include anything else that will help reviewers and consumers understand the change.

  • Does this change depend on other changes elsewhere?
  • Any special concerns or limitations? For example: deprecations, migrations, security, or accessibility.

Best Practices Checklist

We're trying to move away from some deprecated patterns in this codebase. Please
check if your PR meets these recommendations before asking for a review:

  • Any new files are using TypeScript (.ts, .tsx).
  • Deprecated propTypes, defaultProps, and injectIntl patterns are not used in any new or modified code.
  • Tests should use the helpers in src/testUtils.tsx (specifically initializeMocks)
  • Do not add new fields to the Redux state/store. Use React Context to share state among multiple components.
  • Use React Query to load data from REST APIs. See any apiHooks.ts in this repo for examples.
  • All new i18n messages in messages.ts files have a description for translators to use.
  • Imports avoid using ../. To import from parent folders, use @src, e.g. import { initializeMocks } from '@src/testUtils'; instead of from '../../../../testUtils'

Copy link

codecov bot commented Aug 7, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.51%. Comparing base (0e1550a) to head (96bf7fb).
⚠️ Report is 18 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2358      +/-   ##
==========================================
+ Coverage   94.44%   94.51%   +0.06%     
==========================================
  Files        1169     1171       +2     
  Lines       25102    25147      +45     
  Branches     5473     5498      +25     
==========================================
+ Hits        23708    23768      +60     
+ Misses       1328     1316      -12     
+ Partials       66       63       -3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@ahtesham-quraish
Copy link
Contributor Author

@bradenmacdonald I have refactored this file src/files-and-videos/generic/EditFileErrors.jsx as well but there is code coverage issue for the code which I did not touch.

@bradenmacdonald
Copy link
Contributor

@ahtesham-quraish It would be best to update the tests to include clicking those dismiss buttons, but since that's not really in scope here you can try adding istanbul ignore next directives to those 4 lines, like this:

dismissError={/* istanbul ignore next */ () => resetErrors({ errorType: '...' })}

@ahtesham-quraish ahtesham-quraish force-pushed the ahtesham/remaining-part/#2298 branch from 38b6ed8 to 96bf7fb Compare August 20, 2025 09:06
@ahtesham-quraish
Copy link
Contributor Author

@bradenmacdonald you can merge this PR. Thanks

@bradenmacdonald bradenmacdonald merged commit 33c445e into openedx:master Aug 20, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants